Certificate documents
Like audio documents, a certificate document is a special, non-chunked document type. Instead of holding knowledge for retrieval, it stores the PEM certificate files used to secure a customer-defined tool's REST call over TLS, and is referenced by name from the tool_certs advanced configuration parameter.
A certificate document lets you:
- verify the tool URL's server certificate against your own CA certificate(s); and/or
- present a client key and certificate for mutual TLS authentication when the tool's server requires it.
For how to apply a certificate document to a tool, see Custom tool certificates.
Preparing the certificate files
Prepare only the files relevant to your use case. All files must be in PEM format and use these exact names:
| File | Purpose |
|---|---|
server.crt
|
CA certificate used to verify the tool server's certificate. To trust multiple CAs, concatenate their certificates one after another in this single file. |
client.key
|
Client private key (unencrypted), for mutual TLS. |
client.crt
|
Client certificate, for mutual TLS. |
Provide server.crt to verify the server, client.key + client.crt for mutual authentication, or all three.
Uploading the files as a document
- In the Navigation pane, expand AI Agents, and then click Documents.
- Click Add new document.
- In the Name field, enter a unique name. This is the name you reference from
tool_certs. - Select Upload File, then click Upload file. In the file picker, change the file-type selector to All files so that
.crt/.keyfiles become selectable, and choose the files you prepared. - Click Create.
The file names matter – upload them exactly as server.crt, client.key, and client.crt.
Certificate documents are not split into chunks and must not be added to the Documents tab of an Agent or Flow. Reference them only by name in the tool_certs parameter.